ARTEMIS-6116 Fix tests for windows OS - #6513

As far as I can tell, the two JDK8/IBM related commits aren't specific to Windows so they shouldn't be associated with ARTEMIS-6116 either.

As far as I can tell, the two JDK8/IBM related commits aren't specific to Windows so they shouldn't be associated with ARTEMIS-6116 either.

You're right - moving these to a separate issue as well.

@jbertram you mentioned you tested my changes as well - what Windows version are you using? I am getting different results on Windows10 and Windows11 it seems.

I was testing on Windows 10, but I went back and tested again after you responded and it looks like the slashes are indeed a real problem.

@jbertram can you review this again and let me know if anything needs changing? I think I solved everything, tested on win10 and win11.
There's only 1 remaining test failing in Artemis Server (on my machines, anyway), but that's because running "main" without arguments hangs on windows instead of exiting:
MainTest.testNull » Timeout testNull() timed out after 5 seconds
Maybe we should solve that behavior in the server code, not just "fix" the test scenario.

Also, the last commit is solving an edge case. Error only happens when user does not have permissions to create symlinks.

p.s. does it make sense to create a github job to run builds/tests on Windows?

Rebased on main.

Most of this looks good. I only have qualms with two commits:

• "Release file handles in MessageSerializerTest" - this appears to be masking an actual leak, at least in regards to the Producer.
• "Replace ':' in filename with '_'" - this appears to have genuine upgrade problems. Lock files created with : will no longer be loaded once this code is changed. This change should include a note in versions.adoc as well as code to detect & rename existing files using :. Alternatively, it may be simpler to just detect the OS and adjust accordingly so that non-Windows use-cases didn't need to change.

I'll merge the rest but I'm dropping these two commits.